COMMENT ⊗   VALID 00005 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 00002
C00005 00003
C00007 00004
C00010 00005
C00011 ENDMK
C⊗;





     Introductory buzzwah handwave statement.


     The new version of the  datacomputer  (which  new  DFTP

uses)  stores  all  data  on the TBM, CCA's new mass memory.

The smallest unit of space that can be allocated on the  TBM

is  one  megabit.   Thus  if  every  user file stored on the

datacomputer occupied a separate datacomputer  node  (as  is

the  case with old DFTP), each such file would use a minimum

of a megabit on  the  TBM.   This  is  grossly  inefficient,

considering  the  size  of  most  files stored via DFTP.  In

order to be more efficient, new DFTP stores a number of user

files  in  one datacomputer node.  Each subdirectory has one

datacomputer node (the '<FILES>' node)  in  which  the  user

files under that subdirectory are stored.


     The result of this many to one mapping is a distinction

between  operations at the datacomputer node level (at which

all took place with old DFTP) and those (below  that  level)

inside   a   datacomputer   node  (the  <FILES>  node  of  a

subdirectory).  Some commands operate only at the node level

(ALLOCATE,  ATTACH,  CHANGE, CONNECT, CREATE, EXPUNGE, LIST,

REMOVE), and some only at the file level (DELETE, DIRECTORY,

GET,  PUT,  UNDELETE).  Those that operate at the node level

take as arguments a path in the form accepted  by  old  DFTP

(see the January 1976 user's manual), with the addition that

a trailing  "**"  indicates  that  all  inferior  nodes  are

desired.   Those  that  operate at the file level accept (an


                                                    Page   2



optional  path  followed  by)  a  user  file   specification

(<file>.<extension>;<version>  or some subset thereof).  The

user need not (in fact cannot) reference  the  <FILES>  node

directly.   All  user file specifications are applied to the

contents of the <FILES> beneath the  appropriate  node  (the

last  node  of  the  path  if a path was specified, else the

CONNECTed node).


     Zum Beispiel...





*CONNECT FORTRAN
 [Old Node]
*STORE FORPAC.F4
 [OK]
*DIRECTORY *.*;*
**TERSE
 FORDNT.F4;1 2313(7)
 FODPAC.F4;1 4342(7)
*DIRECTORY *.*;*
**VERBOSE
 FORDNT.F4;1  
  11-JUL-76 03:40:56 06-OCT-76 19:44:10 2313(7)
 FODPAC.F4;1  
  11-JUL-76 04:52:27 06-OCT-76 19:49:50 4342(7)
*LIST <<**
**TERSE
    CCA
        WRB
            <FILES>
            FORTRAN
                <FILES>
*LIST <<**
**VERBOSE
    CCA
        WRB
            ] MX-U=9.69 CHRG=3.00
            ] IN-N=3 IN-F=2
            ] CREA=760630054630
            <FILES>
                ] B-AL=1.00 USED=0.01 O-AL=1.00 RECS=1
                ] C-AL=0.01
                ] WRIT=760917233828 READ=761005232817

                                                    Page   3



                ] DUMP=760630054841 D-ID=760719215258
                ] CHRG=3.00 VERS=5 MODN=3
                ] DVID=TBM VOID=8
            FORTRAN
                ] MX-U=1000000.00 CHRG=0.00
                ] IN-N=1 IN-F=1
                ] CREA=761006234215
                <FILES>
                    ] B-AL=1.00 USED=0.05 O-AL=1.00 RECS=2
                    ] C-AL=0.01
                    ] WRIT=761006235003 READ=761006235
                    ] DUMP=000000000000 D-ID=000000000000
                    ] CHRG=0.00 VERS=0 MODN=0
                    ] DVID=TBM VOID=8
*DIRECTORY <<*.*
**TERSE
 (SXCF: STAGING FILE DFTP.CCA.WRB."<FILES">)
 WALDO.;1 23(7)
*RETRIEVE <<WALDO
 [OK]



     There are a number of new commands.   LIST  and  REMOVE

are  the  node  level  equivalents  of DIRECTORY and DELETE,

which operate only at the  file  level.   DELETE  no  longer

eliminates  a  file  on  the  spot,  but  rather marks it as

deleted.  Files that are deleted can be seen via the VERBOSE

option  of  the  DIRECTORY  command.   Deleted  files can be

undeleted by using the  you  guessed  it  UNDELETE  command.

Version  numbers  are maintained so that files with the same

name and extension can be  referenced  unambiguously  (these

numbers are unrelated to the TENEX version numbers files may

have).  EXPUNGE makes a fresh copy of the <FILES> under  the

node it takes as its argument, flushing files that have been

marked as deleted.


-------
∨βββ